This pull request primarily focuses on enhancing the retry mechanism in the service handlers (AmazonTranscribeHandler, PacketDumpHandler, SpeechToTextHandler, and TestHandler) and the server's createSpeechHandler function. The changes introduce a retry count, mutex for thread safety, and methods for updating, getting, and resetting the retry count in the service handlers. The server's createSpeechHandler function has been updated to handle retry logic based on the retry count and configuration settings. There are also configuration changes to specify the maximum retries and retry interval.

Here are the most significant changes:

Retry Mechanism Enhancement:

• amazon_transcribe_handler.go, packet_dump_handler.go, speech_to_text_handler.go, test_handler.go: Introduced RetryCount and mu (a mutex for thread safety) in the service handlers. Added methods UpdateRetryCount, GetRetryCount, and ResetRetryCount to manage the retry count. These changes enhance the retry mechanism in the service handlers. [1] [2] [3] [4] [5] [6] [7] [8]
• handler.go: Updated the createSpeechHandler function to handle retry logic based on the retry count and configuration settings. This change enhances the retry mechanism when creating a speech handler. [1] [2] [3]

Configuration Changes:

• config.go, config_example.ini: Replaced the Retry configuration with MaxRetry and RetryIntervalMs. These changes allow specifying the maximum number of retries and the interval between retries. [1] [2] [3]

Error Handling Improvement:

• amazon_transcribe.go, errors.go: Added a Retry field to the SuzuError structure to indicate whether an error is retryable. This change improves error handling by providing more information about the nature of the error. [1] [2]